-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Improve Application Security #1889
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@wereHamster, making these changes primarily due to the BAFU's report, but also generally, to improve overall security. Do you think the added headers make sense? |
I added validation of the data source url so that we could only used urls that are whitelisted in datasourceUrl. I tried with https://www.npmjs.com/package/graphql-constraint-directive but could not make it work and it seems the directive only worked if the field was nested inside an object, which would have required a refactor of places using datasourceUrl. Instead, I used a custom scalar, which also can be used for providing additional validation rules on existing scalars (see https://www.apollographql.com/docs/apollo-server/schema/custom-scalars). |
Thanks @ptbrowne! Looks like this would be a good solution 👍🏼 Did you have issues with |
I do not know, I did not see this note either, could be. Did it work for you ? |
# Conflicts: # app/graphql/query-hooks.ts # app/graphql/resolver-types.ts # yarn.lock
Tightening up security of the application in general: